gw-cache-buster.php: Fixed an issue with Cache Buster plugin causing fatal error.
#1018
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
claygriffiths
approved these changes
Feb 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
⛑️ Ticket(s): https://secure.helpscout.net/conversation/2840306289/77678
Summary
Cache Buster is causing fatal error when the following filter is used with GF Gutenberg Blocks.
add_filter( 'gfcb_enable_cache_buster', '__return_true' );Following fatal error occurs:
PHP Fatal error: Uncaught TypeError: json_decode(): Argument #1 ($json) must be of type string, array given in ...Add an additional check to the logic to ensure
json_decodeis not processed on a value that is already correctly set in thearrayform. For further context, here is a debug snapshot of the values at this code line on a simple gravity forms block: